Update installer with process impact analysis

ABSTRACT

An update installer generates an update display for a user that displays available updates. The user can select updates, and the update installer accesses the business processes corresponding to the user&#39;s project and displays an impact analysis indicating the impact that the selected updates will have on the processes in the system.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of and claims priority of U.S.patent application Ser. No. 14/152,694, filed Jan. 10, 2014, which is abased on and claims the benefit of U.S. provisional patent applicationSer. No. 61/877,856, filed Sep. 13, 2013, and U.S. provisional patentapplication Ser. No. 61/902,093, filed Nov. 8, 2013, the contents ofthese applications are hereby incorporated by reference in theirentirety.

BACKGROUND

Computer systems are currently in wide use. Some such systems arecustomized (some significantly) before they are deployed at an enduser's site. Such systems often also have updates which can beinstalled.

By way of example, some such computer systems include business systems,such as customer relations management (CRM) systems, enterprise resourceplanning (ERP) systems, line-of-business (LOB) systems, etc. In thesetypes of systems, a general business system is first purchased by a useror customer, and the user or customer often makes customizations,extensions or other modifications to that general business system, inorder to obtain their own customized deployment.

Such systems often have updates published for them. The updates caninclude new releases, as well as bug fixes. For instance, when newreleases of the business system are generated, they are often followedby a number of bug fixes for problems that were not fixed prior torelease. The fixes are normally released, piecemeal, as they aregenerated. Periodically, however, a cumulative update package isreleased which includes all of the fixes generated, to that point. Thismay, for example, include hundreds or even thousands of fixes.

When customers wish to apply the fixes from the cumulative update totheir own customer product, they have conventionally had to either applyall of the fixes in the cumulative update, or none of them. There hasnot been any ability to pick and choose which specific customizations toapply, from a cumulative update.

Further, a user may apply multiple different fixes to their product overtime. It can be difficult for the user to know the comprehensive updatestatus of the product. This is not tracked or stored.

Also, in such business systems, it is not uncommon for users to beoperating in multiple different environments. For instance, a user maybe a developer that is operating in a development environment, and atest environment, or multiple development and test environments.Similarly, where a product has been deployed, there may be a productionenvironment as well, among other environments.

It is currently difficult for a user to decide whether to apply anyupdates, and if so, which ones. If the user operates in multipleenvironments, the user may need to apply the selected updates in allenvironments. This is time consuming. Also, the user is unable todetermine how the updates will affect the underlying business processesand objects within the business system, before they are applied.Further, if the user chooses to apply all of the updates in thecumulative update, there are often conflicts. That is, a user'scustomization may conflict with an applied update. It can take the usera great deal of time and effort to resolve such conflicts.

The discussion above is merely provided for general backgroundinformation and is not intended to be used as an aid in determining thescope of the claimed subject matter.

SUMMARY

An update installer generates an update display for a user that displaysavailable updates. The user can select updates, and the update installeraccesses the processes corresponding to the user's project and displaysan impact analysis indicating the impact that the selected updates willhave on the processes in the system.

This Summary is provided to introduce a selection of concepts in asimplified form that are further described below in the DetailedDescription. This Summary is not intended to identify key features oressential features of the claimed subject matter, nor is it intended tobe used as an aid in determining the scope of the claimed subjectmatter. The claimed subject matter is not limited to implementationsthat solve any or all disadvantages noted in the background.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a block diagram of one illustrative update architecture.

FIG. 1A shows one example of a more detailed block diagram of an updateinstaller component.

FIGS. 1B-1 to 1B-3 (collectively referred to as FIG. 1B) show a flowdiagram illustrating one embodiment of the overall operation of thearchitecture shown in FIG. 1.

FIG. 1C is a flow diagram illustrating one embodiment of the operationof the architecture shown in FIG. 1 in generating a business processimpact analysis.

FIG. 1D is a flow diagram illustrating one embodiment of the operationof the architecture shown in FIG. 1 in generating an object and layerlevel impact analysis.

FIGS. 2-33 are illustrative user interface displays.

FIG. 34 shows one embodiment of the architecture shown in FIG. 1deployed in a cloud computing architecture.

FIGS. 35-40 show various embodiments of mobile devices.

FIG. 41 is a block diagram of one illustrative computing environment.

DETAILED DESCRIPTION

FIG. 1 shows a block diagram of one illustrative architecture 100.Architecture 100 includes customer business system 101 (which can be anon premise system, a cloud-based system, or another system).Architecture 100 also illustratively includes life cycle system 200.Business system 101 and life cycle system 200 can illustratively beaccessed by user 114 through user interface displays 115 generatedeither by systems 101 and 200, themselves, or by user device 116. In oneembodiment, user interface displays 115 have user input mechanisms 117that can be actuated by user 114 in order to manipulate and controlsystems 101 and 200.

Customer business system 101 illustratively includes processor 102, datastore 104, user interface component 105, update installer component 106,conflict resolution component 119 and business process component 121.Data store 104, itself, illustratively includes data 108, applications110, business processes 112, workflows 114, and other items 116. In oneembodiment, applications 110 illustratively include the business logicused to run business processes 112 and workflows 114 in business system101. Applications 110 illustratively operate on data 108, which caninclude entities that represent items in the business system 101. Thus,applications 110 can include a general ledger application, inventoryapplication, applications that allow a user to track businessopportunities, track sales or production in a business system, or a widevariety of other business applications. The entities, for instance,include customer entities that represent customers, opportunity entitiesthat represent business opportunities, inventory entities that representinventory items, quote and proposal entities that represent quotes andproposals, etc. The data 108 can include a wide variety of otherentities and data, and those mentioned above are mentioned for the sakeof example only. User 114 (or other users) can illustratively accesscustomer business system 101 in order to perform activities, tasks,workflows, etc. that are done in carrying out the business of theorganization that deploys business system 101.

Life cycle system 200 illustratively includes project information 206,environment information 208 (which can include informationrepresentative of a set of business processes 209 that are used by theuser in customer business system 101), update state tracking information210, services 202-204, update information 203, update recommendationservice 212, impact analysis information 211, code merge information 213and report generator service 214. Services 202-204 can be used byvarious persons in order to identify, track and resolve issues thatarise during various life cycle stages of a project (e.g., from presaleto implementation and maintenance). For instance, as business system 101is designed, built, deployed and tested, the various services 202-204illustratively allow the developers as well as the user organization totrack issues which arise, and to determine whether the user'sexpectations are met when the final instance of business system 101 isdeployed at the organization.

User 114 can illustratively log in to life cycle system 200 to view thevarious information provided by services 202-204. In one embodiment, forinstance, services 202-204 include a service that allows a user toidentify the needs of an organization and the basic functionality thatis provided with a business system and generate a fit gap list thatidentifies the functionality or customizations that need to be made, tothe business system, in order to meet the needs of the customer that isdeploying the business system. The services also illustratively includea diagnostic service that allows life cycle system 200 to identify theparticular environmental information that defines the environment of thedeployed business system 101. For instance, the environmental data mayidentify the version number and identity of the operating system, theversion number of the base system 101, the particular fixes that havebeen applied to system 101, the version number of the database and otherapplication platforms used by business system 101, whether businesssystem 101 is in a production environment, a test environment, a useracceptance testing environment, etc., and a wide variety of otherinformation.

User 114 can access life cycle system 200 to view project information206 that defines the user's projects, environmental information 208 thatincludes the environmental data mentioned above, as well as anindication of the set of businesses processes 209 that are run onbusiness system 101, update tracking information 210 that identifies theupdate state of business system 101 (for example, which updates havebeen applied and when), update information 203 that indicates availableupdates or detailed information corresponding to updates that have beeninstalled, update recommendation service 212 that recommends updates forbusiness system 101 based upon the information gathered from businesssystem 101, impact analysis information 211 that shows the affect thatselected updates have on business system 101 (such as the businessprocesses 112, the objects, layers, etc.), code merge information 213that shows the affect of automatic conflict resolution. and reportgenerator service 214 that can be used to generate various reports thatare discussed in greater detail below.

Before describing the overall operation of architecture 100 in moredetail, a brief overview will be provided to enhance understanding.Cumulative updates 120 may intermittently become available to updatecustomer business system 101, and specifically the applications 110 orinformation in data store 104, in system 101. The cumulative updates 120may include hot fixes or a variety of other updates as well. In oneembodiment, update installer component 106 uses user interface component105, to generate user interface displays 115 that allow user 114 toselect the various updates that are desired, and to also see an impactanalysis which indicates the impact (e.g., in terms of potentialconflicts) of those updates on the user's business system 101. Updateinstaller component 106 also illustratively allows user 114 to searchfor various updates based on subject matter or otherwise, and to viewthe impact on the business processes 112, as well as to save selectedupdates for replay (or application) in other environments. Updateinstaller component 106 also illustratively installs the selectedupdates, and can automatically resolve conflicts, when commanded to. Theupdate state of customer business system 101 is illustratively uploadedto life cycle system 200 as update state tracking information 210. Thus,user 114 can also log on to life cycle system 200 in order to view theupdate state tracking information 210 and to receive recommended updatesfrom update recommendation service 212, and to view various otherinformation and reports as described in greater detail below.

FIG. 1A is a block diagram of one example of a more detailed embodimentof update installer component 106. FIG. 1A shows that update installercomponent 106 illustratively includes update search component 130,technical impact analyzer component (or impact analyzer component) 132,business process analyzer component 134, installation engine 136, andreply component 138. It can include other components 140 as well. Updatesearch component 130 allows the user to search for updates. Impactanalyzer component 132 allows the user to see the impact of selectedupdates on objects and layers in business system 101, before they areapplied. Business process analyzer component 134 allows the user to seethe impact of selected updates on business processes in system 101,before they are applied. Installation engine 136 installs selectedupdates, and replay component 138 replays (or installs) the selectedupdates in other environments.

FIGS. 1B-1 to 1B-3 (collectively referred to as FIG. 1B) show a flowdiagram of one exemplary embodiment of the overall operation ofcomponent 106 and architecture 100 shown in FIG. 1. FIGS. 1 to 1B willnow be described in conjunction with one another.

In order to begin installing updates, user 114 first launches updateinstaller component 106. This is indicated by block 250 in FIG. 1B.Update installer component 106 illustratively generates a variety ofdifferent preliminary user interface displays that can be viewed by theuser. This is indicated by block 252. Update installer component 106also generates user interface displays that allow the user to select agiven environment to which the updates are to be applied. This isindicated by block 254. The user interface displays can also allow theuser to select the type of installation (such as an express installationin which all updates are automatically applied, or an advancedinstallation in which user 114 can optionally log into user life cyclesystem 200 to identify the particular updates that the user wishes toapply). Selecting the type of installation is indicated by block 256 inFIG. 1B.

FIGS. 2-12 show exemplary user interface displays representative ofupdate installer component 106 generating the preliminary user interfacedisplays, and the set of user interface displays that allow the user toselect the environment and the type of installation. FIG. 2 shows oneexample of a user interface display 258. Display 258 illustrativelyincludes an introductory display pane 260 that shows an introductorymessage that explains that the user can use the following user interfacedisplays in order to apply selected updates from a cumulative updatepackage. Display 258 also illustratively includes a navigation pane 262which displays the various steps that the user will go through in orderto apply the updates.

FIG. 3 shows a user interface display that can be generated when theuser actuates the “next” button 264 in the display of FIG. 2. Some ofthe items shown in FIG. 3 are similar to those shown in FIG. 2, and theyare similarly numbered. FIG. 3 shows display 266. Display 266 shows thatthe user has advanced to the “software license terms” node in pane 262.Thus, pane 260 illustratively displays a set of license terms. The usercan accept the license terms by actuating button 266. The user can thuscontinue with the updating process.

FIGS. 4-6 are exemplary user interface displays that allow the user toselect an update package that is to be applied (or from which certainupdates are to be applied) to business system 101. Display 268 showsthat the user has now advanced to the “select packages” node in pane262. Display 268 also includes a packages display portion 270 and adetails pane or display portion 272. Packages display portion 270illustratively displays update packages that can be applied to thevarious components in business system 101. Details pane 272illustratively displays details corresponding to the packages displayedin portion 270. For instance, in the embodiment shown in FIG. 4, detailspane 272 indicates that the updates corresponding to the “applicationobject server” node 274 in packages pane 270 have already beeninstalled.

FIG. 5 shows an exemplary user interface display 276 where user 114 hasselected or highlighted the “data import/export framework” node 278 inpane 270. Selecting one or more update packages is indicated by block257 in the flow diagram of FIG. 1B. It can thus be seen that the detailspane 272 is updated to display detailed information about thehighlighted node 278. When the user actuates next button 280, the userwill illustratively be navigated to a prerequisite user interfacedisplay, such as display 282 shown in FIG. 6. Display 282 displaysprerequisites (generally shown at 284) that are needed in order toinstall the update packages selected by the user in the display of FIG.5.

Referring again to the flow diagram of FIG. 1B, once the user hasselected one or more update packages for application to business system101, update installer component 106 illustratively generates a set ofuser interface displays that allow the user to specify the environmentswhere the updates are to be applied. This is indicated by block 286 inFIG. 1B. FIGS. 7-11 show exemplary user interface displays for doingthis.

FIGS. 7 shows user interface display 288 which asks user 114 to specifya particular account for the update installation process. For instance,in one embodiment, user 114 is asked to enter a username in field 290and password in field 292 that correspond to an account that hasread/write access and administration rights to the various models andother information in business system 101, that are to be updated. Oncethe user has entered this information, update installer component 106illustratively generates a user interface display, such as display 294shown in FIG. 8, that allows the user to specify the name of the serverthat is running the database integration service that will be used toapply the updates. For instance, user 114 can enter a server name infield 296.

When the user does this, and actuates the next actuator, updateinstaller component 106 illustratively generates a user interfacedisplay (such as display 298 shown in FIG. 9) that allows the user tospecify a model store that is to be updated with selected updates. Forinstance, user interface display 298 allows the user to enter (such asby typing or through a drop down menu or otherwise) the data store thatstores the models that are to be updated with user input mechanism 300.The user can also illustratively add a new model store by actuating userinput mechanism 302.

By way of example, if user 114 actuates mechanism 302, update installercomponent 106 illustratively generates a display (such as display 304shown in FIG. 10) that allows the user to enter a server name in field306 and a model store name in field 308, in order to add a server forupdating. At any point during the processing, update installer component106 can generate a user interface display such as display 310 shown inFIG. 11 that updates the user has to the progress of the processingbeing performed.

Once the user has identified the particular update packages that are tobe applied, and the particular environment where they are to be applied,update installer component 106 illustratively generates a user interfacedisplay, such as display 312 shown in FIG. 12, that allows user 114 toselect a type of installation that is to be performed. Receiving a userinput selecting the type of installation is indicated by block 317 inFIG. 1B.

For instance, the user can choose an express installation in which allupdates in the selected update package are be applied. This can be done,for instance, by actuating user input mechanism 314. Selecting allupdates is indicated by block 313 in the flow diagram of FIG. 1B.However, user 114 can also select user input mechanism 316 which allowsthe user to perform an advanced installation in which the user canselect specific application updates (from the selected package) forapplication to the identified environment. Selecting a subset of updatesis indicated by block 315 in the flow diagram of FIG. 1B. When the userindicates that he or she will be selecting a subset of updates,component 106 generates a set of UI displays that allow the user to dothis. Generating user interface display 312 to select a subset ofupdates to install is indicated by block 318 in the flow diagram of FIG.1B. The user can do this in a variety of different ways. For instance,in one embodiment, the user can actuate user input mechanism 320 inorder to log into life cycle system 200 (shown in FIG. 1) to use theinformation in system 200 to select the updates. Logging into life cyclesystem 200 is indicated by block 322 in FIG. 1B.

However, it may be that user 114 has already selected a set of updatesfor application to a different environment (other than the one that waschosen as described above). In that case, user 114 may have saved thoseselected updates as a list that can be applied to other environments.Thus, if the user actuates user input mechanism 324, the user can inputthe update list for application to the newly selected environment. Inone embodiment, when the user actuates mechanism 324, “browse” button326 becomes active and allows the user to enter a file in box 328 forimporting into the update installation process. Importing a saved listof updates is indicated by block 330 in the flow diagram of FIG. 1B.

It is now assumed that the user has actuated user input mechanism 320 toselect individual updates to be applied. In response to the userselecting the advanced installation and logging into life cycle system200, update installer component 106 illustratively generates a userinterface display, such as display 332 in FIG. 13, that allows the userto search for, and select, various updates that are to be applied in theidentified environment. User interface display 332 includes a first setof user input mechanisms 334. User input mechanisms 334 allow the userto either select all updates for application, or to select onlyapplicable updates. When the user selects the user input mechanism toapply only applicable updates, then those which can be accessed,searched and viewed by the user are only the ones targeted for theenvironment that the user has selected, and for the various featuresthat the user has licensed in business system 101.

Display 332 also illustratively includes a set of filter user inputmechanisms 336. Each of the filter user input mechanism 336illustratively allow the user to select one or more items, upon which tofilter the applicable updates. In the example shown, mechanisms 336include a “module” user input mechanism that is shown as a drop downmenu. The module mechanism allows the user to filter the applicableupdates by module. In the embodiment shown in FIG. 3, the user hasselected the “cash and bank management” module.

The “license code” filter mechanism 336 allows the user to filter theapplicable updates by license code elements. Such elements can include,for example, an electronic banking code element, the general ledger codeelement (or application), etc.

The “country context” filter mechanism 336 allows the user to filter theapplicable updates by country context. For instance, systems that aredeployed in one country may not be interested in some updates that weregenerated, in particular, for a system in another country. Thus, theapplicable updates can be filtered by country context.

The “business process” filter mechanism 336 allows the user to filterthe applicable updates based on the business processes to which theyapply. By way of example, in one embodiment, life cycle system 200includes a service 202-204 that uses a business process modeler togenerate a model of the business processes in a given customer businesssystem 101. Thus, the set of business processes 209 for the individualcustomer business system 101 is stored so that the user can view thevarious business processes in system 101. Update installer component 106illustratively accesses the set of business processes 209 from lifecycle system 200 and displays those processes in the user inputmechanism. Thus, the user can select the particular business processesin business system 101 to filter applicable updates.

In the embodiment shown in FIG. 13, user interface display 332 alsoillustratively includes a search user input mechanism 338. In theembodiment shown, input mechanism 338 is simply a text box that allowsthe user to type in keywords or search query terms that are used byupdate search component 130 in update installer component 106 in orderto search through the updates based on the keywords. For example, theuser may search for updates by title, or by update identifier number.The update identifier number may be a knowledge-base reference oranother identifier.

Display 332 also illustratively includes a results display pane 340.Display pane 340 illustratively displays information corresponding tothe applicable updates that are identified by update search component130 in update installer component 106 based upon all of the userselections, filters, and search terms. The returned results (or resultsupdate set) 342 can be grouped in a variety of different ways. Forinstance, the grouping user input mechanism 344 allows the user toselect one of a variety of different sets of sort criteria for sortingthe returned update results displayed in pane 340.

FIG. 13 shows that the resultant update set 342 that is displayed inpane 340 shows a hierarchical tree structure which includes parent nodes346 and 348. Each of the nodes can have child nodes, such as node 350.Each node has an associated check box. In one embodiment, when a parentnode is selected, all of the children nodes, from that parent node, arealso selected. FIG. 13 also shows that each of the parent nodes includesa numerical identifier 352 and 354. The numerical identifiers associatedwith each parent node identify the number of updates that are in theresult set 342 that will be applied to each of those nodes. In theexample shown in FIG. 13, 12 updates in the result set apply to the banknode and 19 updates in the result set apply to the electronic bankingnode.

FIG. 13 shows that child node 350 corresponds to a given update set. Theupdate set has an update identifier 356 and an update description 358.The identifier is a unique identifier for the given update (or updateset) and the description describes how the update will affect the parentnode.

FIG. 13 also illustratively includes a more detailed information section360. In the embodiment shown, section 360 includes a details tab 362 anda conflicts tab 364. When the user focuses on a parent node in resultpane 340, the details tab 362 may illustratively be empty. Conflictresolution component 119 in business system 101 illustratively generatesa conflict summary display that shows a summary of conflicts for all ofthe updates under the selected parent node. This is described in greaterdetail below with respect to FIGS. 16 and 17.

When the user selects or focuses on a non-patent node in pane 340 (suchas on node 350) then details tab 362 displays details corresponding tothe selected non-parent node. In the embodiment shown in FIG. 13, forinstance, details tab 362 displays details corresponding to the updateidentified by update identifier 356. The details illustratively includethe update identifier 356, the summary description 358, the models 360that are affected by the update, the layers 362 that are affected by theupdate, and any other updates 364 that are included within the selectednode 350.

Also, when the user focuses on a non-parent node in pane 340, theconflicts tab 364 illustratively shows a conflict summary for thatparticular non-parent node (e.g., corresponding to the particular updateidentified by identifier 356). Again, this is described in greaterdetail below.

It will also be noted that, in another embodiment, update installercomponent 106 can display recommended updates, automatically, given theuser's particular environment and configuration information stored inlife cycle system 200.

Returning again to the flow diagram of FIG. 1B, showing recommendedupdates is indicated by block 366, showing a list of all availableupdates (such as when the user selects the “all updates” user inputmechanism 334) is indicated by block 368, displaying a search user inputmechanism 338 is indicated by block 370, allowing the user to group andfilter the search results by applicability, module, country context,configuration, etc., is indicated by block 372 and allowing the user toselect available updates in other ways is indicated by block 374.

FIG. 14 is similar to FIG. 13, and similar items are similarly numbered.However, FIG. 14 is provided to explicitly illustrate that the filteruser input mechanisms 336 can each allow the user to select multiplefilters. For example, the “license code” user input mechanism allows theuser to choose one or all of the “bank” code element, the “electronicbanking” code element, or the “general ledger” code element. These areexemplary only and other items can be used as well.

FIG. 15 shows another user interface display. Display 380 is similar todisplay 332 (discussed above), and similar items are similarly numbered.However, it can be seen that display 380 also provides an indication asto what type of impact the selected updates in the result set displayedin result pane 340 will have on the underlying customer business system101, if they are applied. Generating the view of how the system will beaffected if the selected updates are installed (or applied) is indicatedby block 382 in the flow diagram of FIG. 1B.

In one embodiment described herein, the impact of the selected updateson business system 101 can be shown in these different ways: the impacton the business processes, the impact on the objects and layers ofbusiness system 101, and the level of conflicts that will be generated.In one embodiment, business process analyzer component 134 in updateinstaller component 106 illustratively generates a business process heatmap that identifies the business processes in business system 101 thatwill be affected by the selected updates. This is indicated by block 384in the flow diagram of FIG. 1B. In another embodiment, impact analyzercomponent 132 in update installer component 106 displays an analysis ofwhich objects and layers in business system 101 will be most affected bythe selected updates. This is indicated by block 386 in FIG. 2. Conflictresolution component 119 (in FIG. 1) can also generate a display of aconflict summary or conflict details that will arise if the selectedupdates are applied. This is indicated by block 388. Each of these willnow be described.

The affect of the selected updates on the underlying business processwill first be described. Referring again to the user interface display380 of FIG. 15, it can be seen that the user has elected to group thereturned result set shown in pane 340 by business process. This can bedone by making that selection using the sort or group-by user inputmechanism 344. Thus, the result set is grouped by business process. Theset of parent nodes (with corresponding check boxes 392) each representa business process that will be affected if the selected updates areinstalled. Each parent node has a numerical indicator 394 thatidentifies the number of updates that affect the corresponding businessprocess. For example, the “develop vision and strategy” business processwill be affected by 89 updates. On the other hand, the “manage customerservice” business process will be affected by one update.

The hierarchical structure in pane 340 also shows that each of theparent nodes in the result set includes a heat map indicator 396. In theembodiment shown in FIG. 15, the heat map indicator is a color-codedvisual element that identifies the underlying business processes insystem 101 that will be affected by the selected updates, and the degreeto which they will be affected. For instance, if the indicator 396corresponding to a given parent node is colored red, that may indicatethat the corresponding business process (corresponding to that parentnode) will be greatly affected by the selected updates. If it is yellowor green, on the other hand, that may indicate that the underlyingbusiness process will be less affected or least affected, respectively.

The thresholds for determining whether a parent node has a heat mapindicator 396 indicating that it will be greatly affected or lessaffected can be set in a variety of different ways. For instance, theycan be set anecdotally, they can be set based on user preference (forinstance, a user may identify certain business processes as moreimportant than others), they can be set heuristically, or in other ways.For example, in one embodiment, the top 20% most affected parent nodesmay have a red heat map indicator 396. That is, if the total number ofupdates that will be applied to a given process is in the top 20% of allof the business processes, that given process is assigned a heat mapindicator 396 that indicates that it will be one of the most affectedbusiness processes. The parent nodes with the next 60% of updatesapplied may be assigned an intermediate heat map indicator 396indicating that they will be less affected than the most severelyaffected business processes. The parent nodes with the bottom 20% ofupdates applied to them may be given a heat map indicator 396 indicatingthat they will be least affected, among the various business processes.Of course, this is an exemplary breakdown only, and a wide variety ofother thresholds or breakdowns can be used.

Before continuing with the description of FIG. 1B, FIG. 1C will now bedescribed. FIG. 1C is a flow diagram illustrating one embodiment of theoperation of business process analyzer component 134 in generating thebusiness process heat map shown in FIG. 15. In one embodiment, user 114first accesses life cycle system 200. This is indicated by block 400.This can be done in a wide variety of ways, such as by providingauthentication information 402 or other information 404. This allowsbusiness process analyzer component 134 to access the information insystem 200 in order to perform its analysis. The system then generates aview of the business processes in system 101. For instance, when theuser accesses the business process filter input mechanisms 336, thevarious business processes that the user can choose from are displayedthere. Generating a view of the business processes is indicated by block406 in FIG. 1C. The update installer component 106 then receives thevarious user inputs to select the business processes used in filtering,and to otherwise select the applicable updates. This is indicated byblock 408. Business process analyzer component 134 then generates thedisplay (e.g., the heat map) showing the impact of the selected updateson the business processes, as filtered by the user input selections withthe business process filter input mechanisms 336. This is indicated byblock 410.

Generating a display to show the level of conflicts that will be createdby the selected conflicts will now be described. FIGS. 16-18 showvarious user interface displays that can be generated by conflictresolution component 119 in order to display the various conflicts thatwill be encountered if the user applies the selected updates to theidentified environment in business system 101. It is first assumed thatthe user has selected parent node 348 in result display pane 340 (whichwill automatically select the child nodes, such as child node 350). Itis also assumed that the user has actuated the conflicts tab 364.Conflict resolution component 119 then analyzes the various conflictsthat will be generated in the portions of business system 101represented by parent node 348, and its corresponding child nodes 350.Of course, the system can generate a progress display 412, as desired.

FIG. 17 shows that conflicts tab 364 is now populated with conflictsummary information 414 that summarizes the various conflicts that willoccur in the part of system 101 corresponding to parent node 348 andcorresponding to child nodes 350. It can be seen, for instance, thatconflicts will be generated in two tables, five classes, four forms, noreports, and three other elements. Conflicts tab 364 also illustrativelyincludes a conflict details user input mechanism 416. If the useractuates mechanism 416, conflict resolution component 119 illustrativelygenerates a conflict details display such as that shown in FIG. 18. Itcan be seen that the display in FIG. 18 includes conflict details pane418. Conflict details pane 418 identifies the update (or update model)generally at 420 that may conflict with objects in the model store (orenvironment) selected by the user. The conflict information includes,for instance, the particular layer 422 that may have a conflict, theaffected model 424, the object type 426, the object name 428, and anidentification of the number of conflicts 430. In one embodiment, pane418 also includes user input mechanism 432 that allows the user to viewthe objects that are affected by the updates, even if there are noconflicts identified.

Generating a display showing object and layer level impact will now bedescribed. It may be that the user wishes to view a more detailed impactanalysis that shows the particular layers, models, object types, andspecific objects, that are affected by the selected updates. In doingso, the user can illustratively actuate impact analysis wizard userinput mechanism 434 in order to invoke impact analyzer component 132 inupdate installer component 106. When the user does this, impact analyzercomponent 132 generates an impact analysis pane such as pane 436 shownin FIG. 19. Pane 436 illustratively includes a navigation section 438that allows the user to see where the user is in the impact analysisflow. Pane 436 also illustratively includes an update display 440 thatshows the particular updates 442 for which the impact analysis is beingperformed. The user can verify this information and actuate next button444. Impact analyzer component 132 then generates user interface display446 that allows the user to select a client configuration orconfiguration file to be used in performing the impact analysis. Theuser can illustratively select a client configuration using user inputmechanism 448 and a configuration file using user input mechanism 450.Once the client configuration is selected, the user can illustrativelyactuate next button 444. This causes impact analyzer component 132 togenerate user interface display 452 shown in FIG. 21, which allows theuser to select a model store which will be used in performing the impactanalysis. The user can select one of a number of model stores that aredetected in system 101 using user input mechanism 454. The user can alsospecifically identify a different model store using input mechanism 456.The user can then actuate next button 444.

This causes impact analysis component 132 to generate a pane 458 shownin FIG. 2. Pane 458 allows the user to select a baseline model store,associated with the selected client configuration, the model store holdsthe particular update or update set that is to be analyzed by impactanalyzer component 132. The user can illustratively select a model storethat has been detected using input mechanism 460. The user can alsoillustratively select an existing baseline model store using inputmechanism 462, or the user can create a new baseline model store usinginput mechanism 464. Once the user has identified the baseline modelstore that holds the particular update or update set to be analyzed, theuser can illustratively actuate next button 444. At any point during theprocessing, the system can illustratively generate a progress indicator,such as indicator 460 shown in FIG. 23.

In any case, impact analyzer component 132 then displays the overallconfiguration that the user has identified for analysis. This can bedone by generating a display, such as display 466 shown in FIG. 24.Display 466 illustratively displays a summary 468 of the selectedconfiguration and explicitly indicates that the baseline model storewill be written over at 470. Display 466 also illustratively allows theuser to select the layers to be analyzed by impact analyzer component132 using input mechanism 472. For instance, the user can select theanalysis to be performed on all layers that are affected by the selectedupdates, or on only those layers that have conflicts, as examples.

When the user actuates start analysis button 474, impact analyzercomponent 132 performs the impact analysis, to generate informationindicative of how the selected updates will impact the model files andother parts of system 101, in the configuration specified by the user.In doing so, impact analyzer component 132 can generate progress updatedisplays, such as display 476 shown in FIG. 25. By way of example,display 476 is showing that impact analyzer component 132 is currentlyimporting the update models into the baseline model store. This is showngenerally at 478.

Once impact analyzer component 132 has completed its analysis, itillustratively generates an impact display that displays the impactinformation. The impact information generally indicates the impact thatthe selected updates will have on the objects identified by the user.One example of an impact analysis display is display 480 shown in FIG.26. Display 480 illustratively includes a hierarchical structure 482that identifies the particular impacted objects. The structure 482 notonly identifies the model files at node 484, but also the classes atnode 486 and sub-classes at 488. Of course, a wide variety of otherinformation can be identified as well. In addition, should the user wishto examine the results of the analysis, the user can illustrativelyactuate results button 490 to view more detailed results.

FIG. 1D is a flow diagram illustrating, in more detail, one embodimentof the overall operation of impact analyzer component 132 in performingthe impact analysis that the selected updates will have on theidentified configuration of system 101. Impact analyzer component 132first receives an input invoking it to perform an analysis. This isindicated by block 492. This can be done, for example, by having theuser actuate the impact analysis wizard button in FIG. 18. Component 132then receives configuration inputs from the user identifying a selectedclient configuration (or environment). This is indicated by block 494and is described above with respect to FIG. 20. Component 132 thenreceives user inputs identifying a location of the models to beanalyzed. This is indicated by block 496 and is described above withrespect to FIG. 21. Component 132 then receives an input identifying alocation of the baseline model store that holds the updates to beanalyzed. This is indicated by block 498 and is described above withrespect to FIG. 22. Impact analysis component 132 then performs theanalysis to identify the impact of the selected updates on the selectedenvironment. This is indicated by block 500. Component 132 then displaysthe analysis of the affected objects based upon the selected updates andselected environment. This is indicated by block 502.

The displayed information can take a wide variety of different forms.For instance, it can identify the objects that will be changed asindicated by block 504. It can identify objects or conflicts that existas indicated by block 506. It can also include a wide variety of otherinformation such as the particular update identifier that caused theimpact, the update model, the affected model, the layer, object type,object name, and number of conflicts, among other information. This isindicated at block 508. Impact analyzer component 132 can then store theimpact analysis information, for the selected updates, for later use.This is indicated by block 510 in FIG. 1D. It can be stored oninstallation of the selected updates as indicated by block 512, or itcan be stored at other times as well, as indicated by block 514.

Continuing on with the description of the flow diagram of FIG. 1B, user114 can, at any time, view the current update state or history forsystem 101 by accessing update state tracking information 210 in lifecycle system 200. This is indicated by block 390 in the flow diagram ofFIG. 1B.

At this point in the description, the user has now selected a potentialset of updates to be applied (or installed) and has reviewed not onlythe impact that the selected updates will have on the set of businessprocesses in business system 101, but the impact it will have on theobject and layer levels as well. The user has reviewed the conflictsthat will be generated and can review even detailed informationcorresponding to the impact and to the conflicts. Thus, it may be that,after reviewing this information, the user wishes to select differentupdates and view the impact that they will have. This is indicated byblock 516 in FIG. 1B. If this happens, processing reverts to block 318,where the user can select different updates. If not, however, then thecurrent update selection is saved. It can be saved along with impactanalysis information 211 that shows the impact that the selected updateswill have on the business processes 112 in system 101 and on the objectsand layers in system 101. This is indicated by block 518. The updateselection is saved so that it can be exported for application in otherenvironments as well.

By way of example, update installer component 106 can generate a userinterface display, such as display 520 shown in FIG. 27. Display 520includes an updates display pane 522 that shows the updates that havebeen selected for installation by the user. Display 520 alsoillustratively includes an export user input mechanism 524 that allowsthe user to export the selected updates so that they can be used laterto speed up applying updates on another computer or in a differentenvironment that the user accesses. When the user actuates inputmechanism 524, the user is illustratively allowed to browse using userinput mechanism 526 for a location where the list of updates is to beexported. The user can select the location for export and this willillustratively appear is box 528. The selected updates are exported (orsaved) to that location.

When the user is ready to install the updates, installation engine 136illustratively generates a user interface display, such as display 528that allows the user to confirm that the updates are to be installed.Display 528 illustratively includes a components display pane 530 whichidentifies the particular components that will be updated by theselected updates. Details display pane 532 displays relevant detailscorresponding to the installation process. For instance, in theembodiment shown in FIG. 28, pane 532 indicates that some instances willbe stopped during the update process, and it allows the user toautomatically restart those instances after installation.

Once the user has confirmed that installation is to commence, the usercan illustratively actuate install button 534. This causes installationengine 136 to install the selected updates. This is also indicated byblocks 536 and 538 in the flow diagram of FIG. 1B. During installation,installation engine 136 can generate a progress update display, such asdisplay 540 shown in FIG. 29. Of course, other progress update displayscan be shown as well.

When installation engine 136 completes installing the updates, it alsoillustratively updates the update state tracking information 210 in lifecycle system 200. This is indicated by block 542 in the flow diagram ofFIG. 1B. Installation engine 136 then generates a user interfacedisplay, such as display 544 shown in FIG. 30 that displays the statusof the installation. It can be seen, for example, that the updates tosome of the various components have been successfully installed, whilethe updates to others have not been successfully installed. If the userwishes to view more details, the user can illustratively actuate userinput mechanism 546 to be navigated to a more detailed log file thatshows the details of the corresponding installation.

After the installation is complete, conflict resolution component 119illustratively generates a user interface display that allows the userto request that conflict resolution component 119 will automaticallyresolve as many conflicts as it can, without user intervention.Resolving conflicts is also referred to herein as performing a codemerge. Displaying the user interface display allowing the user to selectautomatic conflict resolution (or code merging) is indicated by block548 in the flow diagram of FIG. 1B. FIG. 31 shows one example of userinterface display 550 that indicates this.

Display 550 includes user input mechanism 552 that can be actuated bythe user in order to indicate that the user wishes conflict resolutioncomponent 119 to automatically resolve conflicts, where possible. Whenthe user actuates mechanism 552, conflict resolution component 119illustratively generates a display, such as display 554 shown in FIG.32. Display 554 allows the user to name the particular merge projectname using input mechanism 556. Conflict resolution component 119 thenperforms the automatic conflict resolution. This is indicated by blocks558 and 560 in the flow diagram of FIG. 2.

The conflict resolution component 119 can do this in a variety ofdifferent ways. For instance, it may be that the base system of businesssystem 101 offered by the manufacturer of system 101 is being updatedwith cumulative update package 120. Thus, there may be an original baseversion of system 101, that is updated to obtain an updated version ofsystem 101. However, it may also be that the organization deployingsystem 101 has modified or otherwise customized the base version ofsystem 101. Thus, in one embodiment, conflict resolution component 119does a three-way compare that compares the original base version ofsystem 101, with the updated version of system 101, and with thecustomized version of system 101 that is actually deployed at theorganization. Conflict resolution component 119 then performs operationsso that the customized version of system 101 that is actually deployedwill be updated in a way to eliminate conflicts.

An example may be helpful. For instance, assume that the base version ofsystem 101 has an element named “string S clock”. Assume that the userhas customized the base version of system 101 so that the element in thedeployed version of system 101 is now called “string S+1 clock”. If theparticular update being installed by the user changes the value of“string S clock” in the base version of system 101, then there is aconflict because the user has already customized that element to “stringS+1 clock”. Thus, conflict resolution component 119 does a three-waytext based comparison to revise the update so that it is consistent withthe user's customization of “string S clock” to “sting S+1 clock”.Performing a multi-level text based comparison is indicated by block 562in the flow diagram of FIG. 1B. Of course, conflict resolution component119 can resolve conflicts in a wide variety of other ways as well, andthis is indicated by block 564.

Conflict resolution component 119 then stores conflict resolution (orcode merge) results information so that it can be reviewed, or used,later. This is indicated by block 566 in the flow diagram of FIG. 1B.For instance, component 119 can store the object path where the mergewas performed as indicated by block 568. It can store the total numberof conflicts 570, the number of resolved conflicts 572, and a time stamp574. Of course, if can store other information 576 as well. This can bestored as code merge information 213 in life cycle system 200, orelsewhere.

The code merge information 213 can be used by the manufacturer ofbusiness system 101, update installer component 106 and/or conflictresolution component 119, or others. For instance, it can be used toimprove conflict resolution, add more features based on what is normallycustomized by the user, or other things.

Conflict resolution component 119 then generates a display of theconflict resolution (or code merge) results information for review bythe user. This is indicated by block 578. FIG. 33 shows one embodimentof such a display 580. Display 580 illustratively includes an unresolvedconflicts display section 582 and a merged (or resolved) conflictssection 584. Both sections show the items or elements where conflictsstill exist or where they have been resolved.

In one embodiment, the information in sections 582 and 584 is displayedin terms of user-actuatable input mechanisms. Therefore, when the useractuates one of the items, the user can be navigated to the codelocation in the code of business system 101 where the conflictsoccurred. The user can thus view the details corresponding to thoseconflicts, or actually work to resolve the conflicts directly from thatdetailed display screen. For instance, if the user actuates the classdeclaration node 586 on display portion 582, the user will be navigatedto that particular class that contains an unresolved conflict, so thatthe user can view and work to resolve the conflict. Receiving a userdrill down input in this manner is indicated by block 588 in the flowdiagram of FIG. 2, and navigating the user to the code location isindicated by block 590.

It will also be appreciated that, where the user has exported theselected updates, they can be applied using the overall operation shownin FIG. 1B, in other environments as well. For example, at block 318,instead of selecting individual updates, the user can import the savedlist as indicated by block 330. The processing thus continues to flow asshown in FIG. 1B, except that the selected updates will be those on theimported list, instead of other updates.

The present discussion has mentioned processors and servers. In oneembodiment, the processors and servers include computer processors withassociated memory and timing circuitry, not separately shown. They arefunctional parts of the systems or devices to which they belong and areactivated by, and facilitate the functionality of the other componentsor items in those systems.

Also, a number of user interface displays have been discussed. They cantake a wide variety of different forms and can have a wide variety ofdifferent user actuatable input mechanisms disposed thereon. Forinstance, the user actuatable input mechanisms can be text boxes, checkboxes, icons, links, drop-down menus, search boxes, etc. They can alsobe actuated in a wide variety of different ways. For instance, they canbe actuated using a point and click device (such as a track ball ormouse). They can be actuated using hardware buttons, switches, ajoystick or keyboard, thumb switches or thumb pads, etc. They can alsobe actuated using a virtual keyboard or other virtual actuators. Inaddition, where the screen on which they are displayed is a touchsensitive screen, they can be actuated using touch gestures. Also, wherethe device that displays them has speech recognition components, theycan be actuated using speech commands

A number of data stores have also been discussed. It will be noted theycan each be broken into multiple data stores. All can be local to thesystems accessing them, all can be remote, or some can be local whileothers are remote. All of these configurations are contemplated herein.

Also, the figures show a number of blocks with functionality ascribed toeach block. It will be noted that fewer blocks can be used so thefunctionality is performed by fewer components. Also, more blocks can beused with the functionality distributed among more components.

Business system 101 and update component 106 or other items inarchitecture 100 can be on-premise or located (fully or partially) in acloud (public or private) deployment. FIG. 34 is a block diagram ofarchitecture 100, shown in FIG. 1, except that its elements are disposedin a cloud computing architecture 500. Cloud computing providescomputation, software, data access, and storage services that do notrequire end-user knowledge of the physical location or configuration ofthe system that delivers the services. In various embodiments, cloudcomputing delivers the services over a wide area network, such as theinternet, using appropriate protocols. For instance, cloud computingproviders deliver applications over a wide area network and they can beaccessed through a web browser or any other computing component.Software or components of architecture 100 as well as the correspondingdata, can be stored on servers at a remote location. The computingresources in a cloud computing environment can be consolidated at aremote data center location or they can be dispersed. Cloud computinginfrastructures can deliver services through shared data centers, eventhough they appear as a single point of access for the user. Thus, thecomponents and functions described herein can be provided from a serviceprovider at a remote location using a cloud computing architecture.Alternatively, they can be provided from a conventional server, or theycan be installed on client devices directly, or in other ways.

The description is intended to include both public cloud computing andprivate cloud computing. Cloud computing (both public and private)provides substantially seamless pooling of resources, as well as areduced need to manage and configure underlying hardware infrastructure.

A public cloud is managed by a vendor and typically supports multipleconsumers using the same infrastructure. Also, a public cloud, asopposed to a private cloud, can free up the end users from managing thehardware. A private cloud may be managed by the organization itself andthe infrastructure is typically not shared with other organizations. Theorganization still maintains the hardware to some extent, such asinstallations and repairs, etc.

In the embodiment shown in FIG. 34, some items are similar to thoseshown in FIG. 1 and they are similarly numbered. FIG. 34 specificallyshows that systems 101 and 200 can be located in cloud 502 (which can bepublic, private, or a combination where portions are public while othersare private). Therefore, user 114 uses a user device 116 to access thosesystems through cloud 502.

FIG. 34 also depicts another embodiment of a cloud architecture. FIG. 34shows that it is also contemplated that some elements of architecture100 are disposed in cloud 502 while others are not. By way of example,data store 104 can be disposed outside of cloud 502, and accessedthrough cloud 502. In another embodiment, update installer component canalso be outside of cloud 502. Regardless of where they are located, theycan be accessed directly by device 116, through a network (either a widearea network or a local area network), they can be hosted at a remotesite by a service, or they can be provided as a service through a cloudor accessed by a connection service that resides in the cloud. All ofthese architectures are contemplated herein.

It will also be noted that architecture 100, or portions of it, can bedisposed on a wide variety of different devices. Some of those devicesinclude servers, desktop computers, laptop computers, tablet computers,or other mobile devices, such as palm top computers, cell phones, smartphones, multimedia players, personal digital assistants, etc.

FIG. 35 is a simplified block diagram of one illustrative embodiment ofa handheld or mobile computing device that can be used as a user's orclient's hand held device 16, in which the present system (or parts ofit) can be deployed. FIGS. 36-40 are examples of handheld or mobiledevices.

FIG. 35 provides a general block diagram of the components of a clientdevice 16 that can run components of architecture 100 or that interactswith architecture 100, or both. In the device 16, a communications link13 is provided that allows the handheld device to communicate with othercomputing devices and under some embodiments provides a channel forreceiving information automatically, such as by scanning Examples ofcommunications link 13 include an infrared port, a serial/USB port, acable network port such as an Ethernet port, and a wireless network portallowing communication though one or more communication protocolsincluding General Packet Radio Service (GPRS), LTE, HSPA, HSPA+ andother 3G and 4G radio protocols, 1Xrtt, and Short Message Service, whichare wireless services used to provide cellular access to a network, aswell as 802.11 and 802.11b (Wi-Fi) protocols, and Bluetooth protocol,which provide local wireless connections to networks.

Under other embodiments, applications or systems are received on aremovable Secure Digital (SD) card that is connected to a SD cardinterface 15. SD card interface 15 and communication links 13communicate with a processor 17 (which can also embody processor 102 orprocessors in system 200 or device 116 from FIG. 1) along a bus 19 thatis also connected to memory 21 and input/output (I/O) components 23, aswell as clock 25 and location system 27.

I/O components 23, in one embodiment, are provided to facilitate inputand output operations. I/O components 23 for various embodiments of thedevice 16 can include input components such as buttons, touch sensors,multi-touch sensors, optical or video sensors, voice sensors, touchscreens, proximity sensors, microphones, tilt sensors, and gravityswitches and output components such as a display device, a speaker, andor a printer port. Other I/O components 23 can be used as well.

Clock 25 illustratively comprises a real time clock component thatoutputs a time and date. It can also, illustratively, provide timingfunctions for processor 17.

Location system 27 illustratively includes a component that outputs acurrent geographical location of device 16. This can include, forinstance, a global positioning system (GPS) receiver, a LORAN system, adead reckoning system, a cellular triangulation system, or otherpositioning system. It can also include, for example, mapping softwareor navigation software that generates desired maps, navigation routesand other geographic functions.

Memory 21 stores operating system 29, network settings 31, applications33, application configuration settings 35, data store 37, communicationdrivers 39, and communication configuration settings 41. Memory 21 caninclude all types of tangible volatile and non-volatilecomputer-readable memory devices. It can also include computer storagemedia (described below). Memory 21 stores computer readable instructionsthat, when executed by processor 17, cause the processor to performcomputer-implemented steps or functions according to the instructions.Processor 17 can be activated by other components to facilitate theirfunctionality as well.

Examples of the network settings 31 include things such as proxyinformation, Internet connection information, and mappings. Applicationconfiguration settings 35 include settings that tailor the applicationfor a specific enterprise or user. Communication configuration settings41 provide parameters for communicating with other computers and includeitems such as GPRS parameters, SMS parameters, connection user names andpasswords.

Applications 33 can be applications that have previously been stored onthe device 16 or applications that are installed during use, althoughthese can be part of operating system 29, or hosted external to device16, as well.

FIG. 36 shows one embodiment in which device 16 is a tablet computer600. In FIG. 36, computer 600 is shown with user interface display 332(From FIG. 13) displayed on the display screen 602. Screen 602 can be atouch screen (so touch gestures from a user's finger 604 can be used tointeract with the application) or a pen-enabled interface that receivesinputs from a pen or stylus. It can also use an on-screen virtualkeyboard. Of course, it might also be attached to a keyboard or otheruser input device through a suitable attachment mechanism, such as awireless link or USB port, for instance. Computer 600 can alsoillustratively receive voice inputs as well.

FIGS. 37 and 38 provide additional examples of devices 16 that can beused, although others can be used as well. In FIG. 37, a feature phone,smart phone or mobile phone 45 is provided as the device 16. Phone 45includes a set of keypads 47 for dialing phone numbers, a display 49capable of displaying images including application images, icons, webpages, photographs, and video, and control buttons 51 for selectingitems shown on the display. The phone includes an antenna 53 forreceiving cellular phone signals such as General Packet Radio Service(GPRS) and 1Xrtt, and Short Message Service (SMS) signals. In someembodiments, phone 45 also includes a Secure Digital (SD) card slot 55that accepts a SD card 57.

The mobile device of FIG. 38 is a personal digital assistant (PDA) 59 ora multimedia player or a tablet computing device, etc. (hereinafterreferred to as PDA 59). PDA 59 includes an inductive screen 61 thatsenses the position of a stylus 63 (or other pointers, such as a user'sfinger) when the stylus is positioned over the screen. This allows theuser to select, highlight, and move items on the screen as well as drawand write. PDA 59 also includes a number of user input keys or buttons(such as button 65) which allow the user to scroll through menu optionsor other display options which are displayed on display 61, and allowthe user to change applications or select user input functions, withoutcontacting display 61. Although not shown, PDA 59 can include aninternal antenna and an infrared transmitter/receiver that allow forwireless communication with other computers as well as connection portsthat allow for hardware connections to other computing devices. Suchhardware connections are typically made through a cradle that connectsto the other computer through a serial or USB port. As such, theseconnections are non-network connections. In one embodiment, mobiledevice 59 also includes a SD card slot 67 that accepts a SD card 69.

FIG. 39 is similar to FIG. 37 except that the phone is a smart phone 71.Smart phone 71 has a touch sensitive display 73 that displays icons ortiles or other user input mechanisms 75. Mechanisms 75 can be used by auser to run applications, make calls, perform data transfer operations,etc. In general, smart phone 71 is built on a mobile operating systemand offers more advanced computing capability and connectivity than afeature phone. FIG. 40 shows phone 71 with the user interface displayfrom FIG. 12 displayed thereon.

Note that other forms of the devices 16 are possible.

FIG. 41 is one embodiment of a computing environment in whicharchitecture 100, or parts of it, (for example) can be deployed. Withreference to FIG. 41, an exemplary system for implementing someembodiments includes a general-purpose computing device in the form of acomputer 810. Components of computer 810 may include, but are notlimited to, a processing unit 820 (which can comprise processor 102 orthe processor in system 200 or device 116), a system memory 830, and asystem bus 821 that couples various system components including thesystem memory to the processing unit 820. The system bus 821 may be anyof several types of bus structures including a memory bus or memorycontroller, a peripheral bus, and a local bus using any of a variety ofbus architectures. By way of example, and not limitation, sucharchitectures include Industry Standard Architecture (ISA) bus, MicroChannel Architecture (MCA) bus, Enhanced ISA (EISA) bus, VideoElectronics Standards Association (VESA) local bus, and PeripheralComponent Interconnect (PCI) bus also known as Mezzanine bus. Memory andprograms described with respect to FIG. 1 can be deployed incorresponding portions of FIG. 41.

Computer 810 typically includes a variety of computer readable media.Computer readable media can be any available media that can be accessedby computer 810 and includes both volatile and nonvolatile media,removable and non-removable media. By way of example, and notlimitation, computer readable media may comprise computer storage mediaand communication media. Computer storage media is different from, anddoes not include, a modulated data signal or carrier wave. It includeshardware storage media including both volatile and nonvolatile,removable and non-removable media implemented in any method ortechnology for storage of information such as computer readableinstructions, data structures, program modules or other data. Computerstorage media includes, but is not limited to, RAM, ROM, EEPROM, flashmemory or other memory technology, CD-ROM, digital versatile disks (DVD)or other optical disk storage, magnetic cassettes, magnetic tape,magnetic disk storage or other magnetic storage devices, or any othermedium which can be used to store the desired information and which canbe accessed by computer 810. Communication media typically embodiescomputer readable instructions, data structures, program modules orother data in a transport mechanism and includes any informationdelivery media. The term “modulated data signal” means a signal that hasone or more of its characteristics set or changed in such a manner as toencode information in the signal. By way of example, and not limitation,communication media includes wired media such as a wired network ordirect-wired connection, and wireless media such as acoustic, RF,infrared and other wireless media. Combinations of any of the aboveshould also be included within the scope of computer readable media.

The system memory 830 includes computer storage media in the form ofvolatile and/or nonvolatile memory such as read only memory (ROM) 831and random access memory (RAM) 832. A basic input/output system 833(BIOS), containing the basic routines that help to transfer informationbetween elements within computer 810, such as during start-up, istypically stored in ROM 831. RAM 832 typically contains data and/orprogram modules that are immediately accessible to and/or presentlybeing operated on by processing unit 820. By way of example, and notlimitation, FIG. 41 illustrates operating system 834, applicationprograms 835, other program modules 836, and program data 837.

The computer 810 may also include other removable/non-removablevolatile/nonvolatile computer storage media. By way of example only,FIG. 41 illustrates a hard disk drive 841 that reads from or writes tonon-removable, nonvolatile magnetic media, a magnetic disk drive 851that reads from or writes to a removable, nonvolatile magnetic disk 852,and an optical disk drive 855 that reads from or writes to a removable,nonvolatile optical disk 856 such as a CD ROM or other optical media.Other removable/non-removable, volatile/nonvolatile computer storagemedia that can be used in the exemplary operating environment include,but are not limited to, magnetic tape cassettes, flash memory cards,digital versatile disks, digital video tape, solid state RAM, solidstate ROM, and the like. The hard disk drive 841 is typically connectedto the system bus 821 through a non-removable memory interface such asinterface 840, and magnetic disk drive 851 and optical disk drive 855are typically connected to the system bus 821 by a removable memoryinterface, such as interface 850.

Alternatively, or in addition, the functionality described herein can beperformed, at least in part, by one or more hardware logic components.For example, and without limitation, illustrative types of hardwarelogic components that can be used include Field-programmable Gate Arrays(FPGAs), Program-specific Integrated Circuits (ASICs), Program-specificStandard Products (ASSPs), System-on-a-chip systems (SOCs), ComplexProgrammable Logic Devices (CPLDs), etc.

The drives and their associated computer storage media discussed aboveand illustrated in FIG. 41, provide storage of computer readableinstructions, data structures, program modules and other data for thecomputer 810. In FIG. 41, for example, hard disk drive 841 isillustrated as storing operating system 844, application programs 845,other program modules 846, and program data 847. Note that thesecomponents can either be the same as or different from operating system834, application programs 835, other program modules 836, and programdata 837. Operating system 844, application programs 845, other programmodules 846, and program data 847 are given different numbers here toillustrate that, at a minimum, they are different copies.

A user may enter commands and information into the computer 810 throughinput devices such as a keyboard 862, a microphone 863, and a pointingdevice 861, such as a mouse, trackball or touch pad. Other input devices(not shown) may include a joystick, game pad, satellite dish, scanner,or the like. These and other input devices are often connected to theprocessing unit 820 through a user input interface 860 that is coupledto the system bus, but may be connected by other interface and busstructures, such as a parallel port, game port or a universal serial bus(USB). A visual display 891 or other type of display device is alsoconnected to the system bus 821 via an interface, such as a videointerface 890. In addition to the monitor, computers may also includeother peripheral output devices such as speakers 897 and printer 896,which may be connected through an output peripheral interface 895.

The computer 810 is operated in a networked environment using logicalconnections to one or more remote computers, such as a remote computer880. The remote computer 880 may be a personal computer, a hand-helddevice, a server, a router, a network PC, a peer device or other commonnetwork node, and typically includes many or all of the elementsdescribed above relative to the computer 810. The logical connectionsdepicted in FIG. 41 include a local area network (LAN) 871 and a widearea network (WAN) 873, but may also include other networks. Suchnetworking environments are commonplace in offices, enterprise-widecomputer networks, intranets and the Internet.

When used in a LAN networking environment, the computer 810 is connectedto the LAN 871 through a network interface or adapter 870. When used ina WAN networking environment, the computer 810 typically includes amodem 872 or other means for establishing communications over the WAN873, such as the Internet. The modem 872, which may be internal orexternal, may be connected to the system bus 821 via the user inputinterface 860, or other appropriate mechanism. In a networkedenvironment, program modules depicted relative to the computer 810, orportions thereof, may be stored in the remote memory storage device. Byway of example, and not limitation, FIG. 41 illustrates remoteapplication programs 885 as residing on remote computer 880. It will beappreciated that the network connections shown are exemplary and othermeans of establishing a communications link between the computers may beused.

It should also be noted that the different embodiments described hereincan be combined in different ways. That is, parts of one or moreembodiments can be combined with parts of one or more other embodiments.All of this is contemplated herein.

Although the subject matter has been described in language specific tostructural features and/or methodological acts, it is to be understoodthat the subject matter defined in the appended claims is notnecessarily limited to the specific features or acts described above.Rather, the specific features and acts described above are disclosed asexample forms of implementing the claims.

1-20. (canceled)
 21. A computer-implemented method comprising:generating a representation of a user interface display that identifiesa plurality of application updates associated with a target applicationin a computer system and includes an update selection user inputmechanism; prior to applying any of the application updates to thetarget application, based on an indication of user actuation of theupdate selection user input mechanism, selecting a first applicationupdate from the plurality of application updates; generating arepresentation of a first impact display including a first visual impactindicator that indicates a degree to which the first application updateimpacts the target application; based on an indication of user actuationof the update selection user input mechanism, selecting a secondapplication update from the plurality of application updates; andgenerating a representation of a second impact display including asecond visual impact indicator that indicates a degree to which thesecond application update impacts the target application; and applyingat least one of the first or second application update to the targetapplication in the computer system.
 22. The computer-implemented methodof claim 21, wherein selecting a first application update comprisesselecting a first set of application updates, and the first visualimpact indicator indicates a degree to which the first set of updatesimpact the target application, and wherein selecting a secondapplication update comprises selecting a second set of applicationupdates, that is different than the first set, and the second visualimpact indicator indicates a degree to which the second set ofapplication updates impact the target application.
 23. Thecomputer-implemented method of claim 21, wherein the second impactdisplay includes a process identifier corresponding to each of aplurality of different computing processes associated with the targetapplication, each process identifier specifically identifying thecorresponding computing process, and a relative impact indicatorvisually associated with each of the process identifiers, each relativeimpact indicator indicating an impact that the second application updatewill have on the computing process corresponding to the associatedprocess identifier, relative to an impact the second application updatewill have on another of the computing processes associated with thetarget application.
 24. The computer-implemented method of claim 23wherein each relative impact indicator comprises a color-coded elementindicating whether the corresponding process identifier identifies acomputing process that will be affected by the second application updateto a high degree, a medium degree, or a low degree, relative to theother computing process.
 25. The computer-implemented method of claim24, wherein the representation of the second impact display isconfigured to display each relative impact indicator adjacent theassociated process identifier.
 26. The computer-implemented method ofclaim 23, wherein the second impact display comprises a details displayconfigured to display information indicative of how the secondapplication update will affect each computing process.
 27. Thecomputer-implemented method of claim 23, wherein selecting a secondapplication update comprises selecting a set of application updates, andwherein each process identifier comprises a hierarchical display havinga parent node that identifies the corresponding computing process andone or more child nodes that identify which of the second set ofapplication updates affect the computing process identified by theparent node.
 28. The computer-implemented method of claim 26, whereineach relative impact indicator indicates a number of the applicationupdates that will be applied to the computing process corresponding tothe associated process identifier.
 29. A computing system comprising: aprocessor; and memory storing instructions executable by the processor,wherein the instructions, when executed, configure the computing systemto: generate a representation of a user interface display with an updateselection user input mechanism; based on an indication of user actuationof the update selection user input mechanism, select an applicationupdate associated with an application; and generate a representation ofa process impact display that includes a heat map representation thatgraphically represents an impact of the selected application updaterelative to a plurality of computing processes associated with theapplication, the heat map comprising a process identifier correspondingto each computing process and a color-coded element associated with thecorresponding computing process, and indicative of an impact of theselected application update on the corresponding computing process. 30.The computing system of claim 29, wherein the heat map comprises amatrix having the color-coded elements arranged in rows and columns. 31.The computing system of claim 29, wherein each color-coded elementindicates a degree of impact of the selected application update on thecorresponding computing process relative to another computing process.32. The computing system of claim 31, wherein each color-coded elementindicates whether the corresponding computing process will be affectedby the selected application update to a high degree, a medium degree, ora low degree, relative to the other computing process.
 33. The computingsystem of claim 29, and further comprising: based on an indication ofuser actuation of the update selection user input mechanism, selecting aset of application updates associated with the application; wherein eachcolor-coded element indicates a number of updates, in the selected setof updates, that will affect the corresponding computing process. 34.The computing system of claim 29, wherein generate the representation ofthe process impact display comprises: generating the color-codedelements based on a predefined threshold.
 35. The computing system ofclaim 34, wherein the predefined threshold is based on an indication ofa user preference.
 36. A computing system comprising: a processor; andmemory storing instructions executable by the processor, wherein theinstructions, when executed, configure the computing system to: identifya plurality of application updates associated with a target application;and prior to applying any of the application updates to the targetapplication, generate a representation of a user interface display thatincludes an impact display and an update selection user input mechanism;and based on an indication of user actuation of the update selectionuser input mechanism, identify a plurality of different sets of theapplication updates, each set comprising one or more of the applicationupdates; and iteratively update the impact display to indicate, for eachset, a degree to which the one or more application updates in the setimpact the target application.
 37. The computing system of claim 36,wherein the impact display includes, for each set, a process impactindicator that indicates a degree to which the set of applicationupdates will have an impact on a particular computing process associatedwith the target application.
 38. The computing system of claim 36,wherein the process impact indicator indicates a number of applicationupdates that will have an impact on the particular computing processrelative to a number of updates, in the selected set of updates thatwill have an impact on another computing process associated with thetarget application.
 39. The computing system of claim 38, wherein theimpact display includes, for each set, a plurality of process impactindicators, each process impact indicator corresponding to a differentcomputing process associated with the target application.
 40. Thecomputing system of claim 39, wherein the impact display comprises aheat map that includes a color-coded indicator corresponding to eachcomputing process.